No Current Link To VocabularyCoded With ExtensionsCoded No Extensions
COCT_MT050207CA
Patient Person informational

Derived from RMIM: _ and HMD: _
 
Patient
Design Comments: A person who is receiving or may receive healthcare services and has personal attributes (e.g. name, birth date).  
Rationale: Information used to identify the patient and to support clinical decisions. This is used when the patient is not known to the client registry but information still needs to be communicated. E.g. lab or drug reporting to PHS for an unconscious or otherwise unidentifiable patient.  
classCode [1..1] (M)
Patient (CS) {CNE:C:RoleClass:PAT, fixed value= "PAT"}
id [1..3]
Patient (SET<II.PUBLIC>)
Design Comments: Unique identifier assigned to a person, possibly by a local system or some other non-client-registry identifier.  
Rationale: Allows a patient to be referred to unambiguously. Because this CMET deals with patients not confirmable against a client registry, it's possible that no identifier will be known and therefore the attribute is only 'populated'. The cardinality of patient identifiers is up to 3 based on the use case to support communication of a local and jurisdictional identifier along with the national identifier.  
Mapping: C39 (Extension)  
Mapping: PTT.050.01 (Extension)  
Mapping: PTT.050.02 (Root)  
Mapping: A.1  
Mapping: PID.2  
Mapping: Patient.332-CY (Extension)  
Mapping: Patient.331-CX (Root)  
Mapping: Claim.330-CW  
Mapping: Health Card Number  
Mapping: PID.2  
Mapping: PID.4  
Mapping: ZDU.2  
Mapping: ZKW.3  
Mapping: Jurisdiction (Root)  
Mapping: Person.PHN (Extension)  
addr [0..1]
Patient (AD.BASIC)
Design Comments: Physical address for the patient where they may be visited or found.  
UsageNotes: Contact information specific to the patient for a particular action (prescription, lab test, etc.) will be conveyed as part of the payload.  
Rationale: Provides basic contact information for the patient.  
Mapping: ZPA2.1 (use)  
Mapping: ZPA2.2 (usablePeriod(IVL<TS).low)  
Mapping: ZPA2.4 (partType=UNID)  
Mapping: ZPA2.5 (DMODID - following DMOD=P.P.Box)  
Mapping: ZPA2.6 (partType=??)  
Mapping: ZPA2.7 (partType=??)  
Mapping: ZPA2.8 (partType=CTY)  
Mapping: ZPA2.9 (partType=CNT - populate mnemonic of SC)  
Mapping: ZPA2.10 (partType=ZIP)  
Mapping: ZPA2.11 (partType=SINST=PST)  
Mapping: ZPA2.12 (partTYpe=STA)  
Mapping: ZPA2.13 (partType=DMODID-followingDMOD=RR)  
Mapping: ZPA2.14 (partType=DIR)  
Mapping: ZPA2.15 (partType=STB)  
Mapping: ZPA2.16 (partType=BNR) BC:ZPA2.17 (partType=STTYP)  
Mapping: ZPA2.18 (usablePeriod (IVL<TS).high)  
Mapping: ZPA2.19 (Line demarked by carriage return)  
Mapping: PTT.060-01 (partType=SAL)  
Mapping: PTT.060-02 (partType=CTY)  
Mapping: PTT.060-03 (partType=CNT)  
Mapping: PTT.060-04 (partType=ZIP)  
Mapping: PID.11  
Mapping: Patient.322-CM (partType=SAL)  
Mapping: Patient.323-CN (partType=CTY)  
Mapping: Patient.324-CO (partType=STA)  
Mapping: Patient.325-CP (partType=ZIP)  
Mapping: PID.11  
telecom [1..5]
Patient (LIST<TEL.PHONEMAIL>)
Design Comments: Telephone, fax and/or e-mail addresses intended as the principal means of contact for the patient.  
UsageNotes: Contact information specific to the patient for a particular action (prescription, lab test, etc.) will be conveyed as part of the payload.  
Rationale: Provides basic contact information for the patient.Important for following up with patient but not always available, and therefore only marked as 'populated'.  
Mapping: ZPA1.1 (Use and/or URL.scheme)  
Mapping: ZPA1.2 (usablePeriod (IVL<TS>).low) BC:ZPA1.3 (url.address - as per RFC2396)  
Mapping: ZPA1.4 (url.address - as per RFC2396)  
Mapping: ZPA1.5 (usablePeriod (IVL<TS>).high)  
Mapping: PTT.070-01  
Mapping: PTT.070-02  
Mapping: D99.03 (url.address - as per RFC2396)  
Mapping: patient.326-CQ  
Mapping: PID.13  
Mapping: PID.14  
patientPerson [1..1] (Person)
 
Person
classCode [1..1] (M)
Person (CS) {CNE:C:EntityClass:PSN, fixed value= "PSN"}
determinerCode [1..1] (M)
Person (CS) {CNE:C:EntityDeterminer:INSTANCE, fixed value= "INSTANCE"}
name [1..1]
Person (PN.BASIC)
Design Comments: The name by which the patient is known.  
Rationale: Used by to help identify the patient and also when referring to the patientThe element is populated because the patient's name is important for display. However, there may be circumstances where a name is not known by the reporting system.  
Mapping: ZPA.1 (partType=Given)  
Mapping: ZPA.2 (partType=Family)  
Mapping: ZPA.3 (partType=Given - all repetitions except first)  
Mapping: C37 (partType=Given)  
Mapping: C38 (partType=Family)  
Mapping: PTT.030-01 (partType=Family)  
Mapping: PTT.030-02 (partType=Given - 1st occurrence)  
Mapping: PTT.030-03 (partType=Given - subsequen occurrences)  
Mapping: PTT.030-04 (partType=Suffix)  
Mapping: PTT.030-05 (partType=Prefix)  
Mapping: patient Initials  
Mapping: PID.5  
Mapping: Patient.310-CA (partType=Given)  
Mapping: Patient.311-CB (partType=Family)  
Mapping: Recipient Name First (partType=Given)  
Mapping: Recipient Name Last (partType=Family)  
Mapping: PID.5  
Mapping: PID.9 (any name other than first repetition is an alias)  
Mapping: ZDU.3  
Mapping: ZKW.2  
Mapping: Person.givenName  
Mapping: Person.lastName  
Mapping: Person.middleName  
Mapping: Person.namePrefix  
Mapping: Person.nameSuffix  
administrativeGenderCode [1..1]
Person (CV) {CNE:D:AdministrativeGender}
Design Comments: Indicates the gender (sex) of the patient as known by the client registry. Complex genetic genders are handled as observations if they are considered relevant.  
Rationale: Used to confirm patient identity. May affect clinical decision support such as drug dosing, lab test appropriateness, etc.The element is 'populated' because there are some situations where the patient's gender may not be known by the sending system when dealing with non-client registry patients.  
Mapping: C40 eScript:PTT.040  
Mapping: 3  
Mapping: Sex  
Mapping: PID.8  
Mapping: Patient.305-C5  
Mapping: PID.8  
birthTime [1..1]
Person (TS.DATE)
Design Comments: Indicates the date on which the patient was born as known by the client registry.  
Rationale: Used to confirm patient identity.May also influence clinical decision support such as dosage and therapy appropriateness.The element is populated because the patient's birth date may not be known, particularly for patients not found in the client registry.  
Mapping: C34  
Mapping: PTT.020  
Mapping: A.2b  
Mapping: HC-SA  
Mapping: PID.7  
Mapping: patient.304-C4  
Mapping: PID.7